SharePoint's most availing attribute has nothing to do with its features, functions, or custom sleights of hand. The best thing about it? It's that ever-engulfing big SharePoint tent. You can't reach out for a referral or show up at a local workshop without enlisting a new ECM ally...
At the enterprise level, I’ve seen the structured-functional hierarchy of categories in retention schedules (business functions, records series, and record type examples) used as the foundation for enterprise taxonomies. A very limited subset of the record type examples is exposed to end users from which they make a choice
With automatic assignment of retention to electronic records, initially someone has to map retention codes to “controlled vocabulary” in modeled enterprise taxonomies
During his consulting-focused career, Gene has provided clients with expert guidance on matters ranging from enterprise taxonomy development to technical system implementation solutions in the Banking/Finance, Insurance, Healthcare and Utilities sectors
08-16-2023 | 12:30 - 13:30 ET
Let’s start with setting some context on two different methods for classifying information in our enterprises. Taxonomy is defined as a system of classification that is based on a structured and controlled method to annotate and categorize content
That could easily be turned into an enterprise taxonomy project even though it could start by developing small departmental taxonomies
1 Comment - no search term matches found in comments.
Some examples might be: Ensuring the only “portable media” available via the standard procurement channels are the encrypted ones that meet your Information Storage Standard, Configuring your email solution so that it supports your organization’s email policy, (see Mark Mandel’s recent blog on this very important topic: The Email Pyramid Disabling the creation of folders in SharePoint libraries, (as intimated in Daniel Antion’s recent blog: Site vs Library ) Creation of an enterprise taxonomy so that the organization has consistent methods to describe information
The best have governance, usage guidelines, and an enterprise taxonomy in place
I call this the Incremental Enterprise Taxonomy model; work with a small number of key stakeholders to develop a high-level taxonomy for your ECM solution then validate, change and revalidate the taxonomy through the course of each deployment (see Guideline 5 below for more on the care and feeding of your ECM system)